Monster Media 1996 #14/Monster Media No. 14 (April 1996) (Monster Media, Inc.).ISO/bbs_lord/lnet0205.zip/NC.DOC

Text File | 1996-02-05 | 21KB | 531 lines

                 |\| <   documentation


    this documentation is being written by someone who has never been an
    NC, and never intends to be one.  Joseph Masters.

    However, I've been in contact with over 15 different NCs since the
    first alpha version of LordNet (and man was that sorry).

    Finally, LordNet steps out of beta.  It's close enough to bugless for
    me.  For you, well, unless you demand the perfection of shrink-wrapped
    software, I think it'll do the job.

    Anyhow, this is the preamble to the NC.DOC.  NC.DOC is a compilation
    of everything I learned from NCs, and everything I've created for NCs.
    Including little tricks that exist in LordNet that no one knows (except
    the NCs whom I've told).

    One more thing -- most of the documentation, except the Starting section,
    is geared toward Registered LordNet sysops.  To be a proper NC, you
    really need to be registered, almost every special NC option is a
    REGISTERED ONLY feature.  This isn't really to benefit _ME_, it's more
    for security reasons.  It makes it so you'd have to give your reg code
    to someone for them to corrupt your league.




  Table of Contents


  1...............................Starting Your Own League
  2...............................Messing Around with Sites
  3...............................Changing the Lord Game
  4...............................IGMs and Why You Should Dread Them
  5...............................Kicker'em in the Arse
  6...............................The Zen of Using UPDATE.ZIP
  7...............................Resetting the Net
  8...............................What the Heck is an Alternate Address?
  9...............................Announcing Netwide
 10...............................Site Format WHAT?
 11...............................League Taggage, and Why You Want it!
 12...............................FAQ and FGA (Frequently Given Answers)


[1] Starting your own league

    First of all, there are no real requirements to run LordNet as an NC.
    You don't have to have a front end mailer, or a BBS.  Well, you do have
    to have LORD, but the others aren't required.  Read LOCAL.DOC if you
    want to know how to run LordNet through multiple Lord games on one
    BBS.  There is a short explanation on how to run LordNet on multiple
    BBSs without a front end mailer at the end of this section.  Otherwise,
    this next bit is for the sysops who are planning to run through a
    fido-style network.


      1) Unzip LORDNET.ZIP into its own directory.  This means somewhere
         like c:\LNET.  I recommend a directory directly off the root,
         because you'll probably be going there a lot.  Anyhow, it makes it
         easier to type.

      2) Run LORDNET CONFIG (hey, notice how this is like the other configs?)

      3) <E>dit Local Configuration.  Fill out the lines.  The most
         important ones are the Main Node and BBS Name for you.  These go
         into the SITE.DAT file, and are more or less permanant.  Your node
         number doesn't have to exist yet (let's say you're about to get a
         fido address), but it has to be what it will eventually be.  As a
         net coordinator, it really doesn't matter if it exists, if people
         call you for their mail.

      4) <C>reate New NetGame

      5) Pop in <A>lternate Address Config, and quit out.  (Heh, this is
         another trick of the NC!  Don't ask!)

      6) Go into the <N>etwork Coordinator Menu.  Now, if it's unregistered,
         you won't be able to do anything except the Site Editing.

      7) Run the <S>ite Editor, and put in your other sites.  If you don't
         have any, just remember where to do it.

      8) Run THE GENERATOR.  Just accept the defaults, unless you really
         have downlinks under downlinks ALREADY.  After all, you can always
         do it again.  (TIP!  As an NC, you should LEARN what the heck the
         commands in the SITE.DAT are).

      9) <I>nstall LordNet

     10) Edit your BULLETIN.CFG file.  Follow the instructions in it.

     11) Edit your incoming mail batch file, and put INBOUND in it.

     12) Put OUTBOUND in your nightly events file.


  Well, that's the SETUP in a nutshell.  Not really difficult, and now you
  can essentially run your own net without doing much else than sending
  new sites their SITE.DAT files.  But of course, obsessive NC that you
  are (or shall we say concerned NC?), you'll want to use everything in
  LordNet.  So, read on!



[2] Messing Around with Sites

  This section is mainly concerned with the Site Editor and the ROUTE.CFG
  file.  One of the more important areas of this documentation.

    * Adding Sites
      ...Is easy.  Just hit N in the site editor, and LO!  LordNet creates
      a new site with my information in it.  Now, just edit those lines.
      However, when you add a site, I recommend you also crash out a
      SITE.DAT to that site.  Then they can install LordNet into Lord and
      get rolling.  However, whenever giving a site the SITE.DAT file,
      make sure they're in it.  Otherwise it won't do them any good.
      Choose <N>ew Site when you use this option -- <R>estructuring
      is discussed in the FAQ section of this documentation.


    * Deleting Sites
      When you do this, LordNet will tell you it's a deleted site (wow).
      Sorry, no undelete, you'll have to re-type it.  Also, it won't show
      up in LordNet any more.  However, you'll soon notice that your damned
      OUTBOUND is still creating packets and netmail for it.  Hey, that's
      an easy fix!  At the end of your ROUTE.CFG file, add this line:

      LOCAL X 1

      where X is the site number of the deleted site.  Make sure you put it
      at the END of the file.  (NOTE: What this basically does is say,
      "Send site X's info to Site #1.  Hey, wait, I _AM_ Site #1.  So it's
       already here.  Good, I'll skip it!"  The LOCAL is to insure no
      netmail is written).


    * Organizing Sites
      Once you have too many sites to keep in your head all the time
      (generally this begins at 10), you'll need to PRINT OUT a list of
      the sites, from the Site Editor.  Also, go ahead and PRINT OUT a
      list from the SITE FORMAT CONVERSION area.  This gives a list of
      my weird format vs. base 10 numbers (read LORDNET.DOC for more
      information on this).  It will help you keep track of which site
      isn't picking up their mail.


    * Attracting Sites
      One of the best campaigns I've ever seen happened when the NC of a net
      offered to poll *YOU* if you would join his net.  Tons of people
      joined, and he was able to say, "Ok, it's your turn to call me", and
      of course their users demanded that they stay in the net.

      If you don't have that kind of capital, you can almost always find 5-6
      sysops in your area who would love to hook up together and "brawl".

      If you want a national net, find a niche!


    * Magic Special Screen
      For those of you who were wondering, it's ALT-178.




[3] Changing the Lord Game

  In order to keep things fair, LordNet regulates your Lord Game in many
  ways... Well, actually, only three.

    * User Fights
      (Located in [D]efaults)
      Simple to set!  Just tell LORDNET what you want it to be!  I
      recommend anywhere from 7-15.  This is where the inter-bbs play
      becomes fun.  Below 7 is just not very fun.

    * Forest Fights
      (Located in [D]efaults)
      Also simple to set.  I'll recommend anywhere from 0 to 20.  This
      part tends to take away from LordNet, and one of the most successful
      leagues I've ever seen had 3 forest fights a day (and 20 user fights).
      My advice: KEEP IT LOW.

    * Bank Transfers
      (You can set it in LORD, or in [B]ank Transfers)
      Well, this can be an enemy to LordNet, but if your BBS is a team,
      it won't matter much at all.  If you're running a PLAYER vs. PLAYER
      game, then this could be very much a part of Lord.  But things
      generally don't go that way.  My advice?  3 transfers a day,
      100,000 gold limit.




[4] IGMs and Why You Should Dread Them

    Nothing can screw up LordNet like a bad IGM.  Just ONE bad IGM can ruin
  an entire league forever.  That's why you can regulate exactly what can
  and cannot be played in LordNet.

    The IGM Control Booth itself is very simple.  It has a limit of 81
  IGMs, which is pretty close to the amount available.  Last time I counted
  there were about 98 IGMs.  However, IMHO, most of them aren't worth
  unzipping.  This section is not about what IGMs are good, though.  Before
  you approve the IGMs you love, look at a couple of things:

    * If you play this IGM daily, in 10 days, will you be *much* higher up
      than a player who didn't play the IGM?

    * Is this IGM sysop configurable? (to awards)

    * Does the IGM set rewards by level, or is it static numbered?

    * Does this IGM have major bugs?

    If you said yes to any of those, then I think it would be a mistake to
  put it in your APPROVED list.  However, if you approve everything, you
  may get more users (but it will be much more "corrupt").

    As of the issuing of this IGM, I highly recommend three IGMs for
  LordNet.  Two are mine, all are freeware:  Seth's Lotto, Barak's House,
  and Aragorn's Timer.  The impact on your game of these three IGMs might
  even be negative.

    Setting up these IGMs (and others) for approval is quite simple.  Just
  run the IGM Control Booth from the NC Menu, and enter in the names (w/o
  the EXE extension).

    This will go out when you run MAINTENANCE (through LordNet).  Maintenance
  will create a Uxxx001.DAT file for each site, and those will go out when
  you run OUTBOUND.



[5] Kicker'em in the Arse

    When I originally released LordNet, the biggest problem was always
  "What to do with those players sitting at level 12?".  Thus, Kicker was
  created.  Although with the new scores, there's not much incentive to
  stay at level 12, but it's still a problem.

    Kicker allows you to choose the lowest level to check, and then choose
  the number of days a player can remain at each of those levels.  For
  example, if you choose level 10 and 5 days, that means every player
  must beat levels 10, 11, and 12 in 5 days each (15 days for all three).

    Set it in the [K]icker option of the NC Menu.

    I recommend setting for level 9, and give it 7-10 days.  If you run
  a very lenient net, then disable it.



[6] The Zen of Using UPDATE.ZIP

  UPDATE.ZIPs are indeed an ART!  Just look at everything you can put in 'em!
  These are things that would make an impact on Lord & LordNet:

    * LNETXT.DAT
    * LNETRIP.DAT
    * LORDNET.EXE
    * INBOUND.EXE
    * OUTBOUND.EXE
    * ROUTE.CFG
    * LORDTXT.DAT
    * LENEMY.DAT
    * LORDRIP.DAT

    Notice that this allows you to upgrade LordNet underneath their noses,
  after each one of your sites sets up LordNet, s/he can forget about it!
  You can change everything!  You can also change exactly what the both the
  LORD and LordNet Games look like.  You could even do as simple a change as
  changing "(O)ther Places" to "(O)pen LordNet".

    Now, using the UPDATE.ZIP is quite easy.

    1) Create a ZIPped file called UPDATE.ZIP in your main LordNet
       directory.  Put it in all the files you want LordNet to handle.
       (Preferably just the files listed above -- everything you send
       except the LORDRIP.DAT and LORDTXT.DAT go into the main LordNet
       directory.  You do not have to send all of them!).

    2) Run LORDNET CONFIG, Enter the NC Menu.

    3) Choose <U>pdate Net.  Say Yes.

    4) Run OUTBOUND.

    This SHOULD pack out your UPDATE.ZIP to all your sites.  However, if
  for some reason, the update doesn't get passed down all the way, here's
  a thorough explanation of what's happening, so you can inspect what's
  going on.

    a) UPDATE.ZIP is created by you

    b) UPDATE.TXT is created by LORDNET CONFIG's NC menu (when you choose
       <U>pdate Net)

    c) Uxxx001.DAT files are created for the entire net by LORDNET CONFIG.

    d) OUTBOUND finds UPDATE.TXT, and packs UPDATE.ZIP into each packet.
       Then it deletes UPDATE.TXT.

    e) OUTBOUND packs out the U*.DAT files.

    f) INBOUND on your downlinks' computers unzips your packet, finds the
       U*.DAT file.  _THEN_ it looks for the UPDATE.ZIP (in other words,
       both of those files need to exist for it to process the UPDATE.ZIP).

    g) INBOUND processes the UPDATE.ZIP, copies UPDATE.ZIP into its
       main LordNet directory, creates the UPDATE.TXT file, and moves the
       U*.DAT files you created for its downlinks into the LORDNET OUT
       directory.

    h) The process goes on...

    Generally, if it doesn't work, try it again.  Probably a lost file.




[7] Resetting the Net

    This is useful if you're running a tournament-type-thing, to start off
  all the BBSs on the same day.  Basically, you run <R>eset the Net in
  the NC Menu, and you're done!

    Now, since the beginning of this option, I've always gotten people
  saying that it didn't work.  Well, it does.  You may have gotten a lost
  packet or something, which is why you can reset individual nodes.

    If most sites get reset, just send resets down to the sites that haven't
  gotten them yet (Then run OUTBOUND, and crash the packet.  That will
  expedite things).  However, in the two nets I'm in, both had 100% resets
  on a January 1st reset.




[8] What the Heck is an Alternate Address?

    If you are running your net in only one league (in one zone number),
  you can skip this section.

    If people are calling you for their packets, you can skip this part,
  although you may want to show it to people running across nets.

    This is relatively simple.  If you are calling someone in a different
  net than you, all you have to do is enter your node number in that net
  in your Alternate Addresses config.


    For example, I'm in RGS Net and FidoNet.  I run the league through
  FidoNet, but I'm crashing packets to a local sysop in RGS Net.  My
  alternate addresses config will look like:

    1] 1:3666/605
    2] 50:250/300

    The main node number (and site node number) of the sysop in RGS Net will
  be his RGS Net address (let's say it's 50:250/302).

    However, if you're running a FrontDoor - type mailer, and the people in
  the different nets are calling YOU, this isn't really necessary.




[9] Announcing Netwide

    If you want to announce something throughout Lord Games all over your
  net, this is the way to do it.  Everything you type goes into the
  LOGNOW.TXT.  Enter color codes, because they'll work!

    You have a limit of 10 lines.

    This option is accessible through the NC menu, Netwide Announcement.



[10] Site Format WHAT?

    The following is merely an excerpt from the LORDNET.DOC:

            This can be accessed by running LORDNET.EXE CONFIG and choosing
<S>ite Format Conversion. It's purpose is to show the conversion between
the site number and the data file.  Example:

    LNxxLLyy.Znn

    LN - Identifies as LORDNET
    xx - Site TO, in the SITE FORMAT
    LL - League TAG, in the SITE FORMAT
    yy - Site FROM, in the SITE FORMAT
    nn - Number from 01 to 99.

So, what _is_ the SITE FORMAT?  Well, it's like hexadecimal, but instead of
ending on F, it ends on V.  Therefore, 1 is still 1 (actually it's 01), but
10 is A (or 0A).  This allows me to run over 3 digits in a 2 digit space.

        Use the SITE FORMAT CONVERSION to "see" what your package is.  You
could write a simple DOS batch file to separate packets, if you wanted.

        You may print this info out which will show all the sites and their
conversion.


    Okay, so, as a net coordinator, this is just useful for keeping track
  of packages.




[11] League Taggage, and Why You Want It!

    A league tag is a way to allow you to run two different LordNets on
  the same system.  Actually, it allows you to run up to 999 different
  LordNets on the same system, with the same address.

    If you are in two different nets, but they have different zone numbers,
  you don't have to worry about the League Tag.

    If you are in two different nets and have different site numbers in
  both, you don't have to worry about the League Tag.

    In fact, the only case that you DO have to worry about the League Tag is
  if you RUN (i.e. you are the NC) two different LordNet on the same fido-
  style address.  You will also have to worry about it if you're, say, site
  2 for two different leagues that run in the same net.  However, that's a
  very changeable situation, so forget about it.

    So, how DO you run two different Leagues through the same address?  Just
  set the League Tag in one to something other than the other one (wow,
  what a complicated way of saying something easy!)

    For example, if you're running both nets through FidoNet, then one of them
  will more than likely have the League Tag of 1 (your zone number).  Just
  set the other one to something like.. 2.  However, everyone who joins your
  net will have to change their League Tag to 2 as well!

    Here's the process:

    1) LORDNET CONFIG.

    2) [L]eague Tag

    3) Set it to whatever you want, INTEGERS ONLY, from 1 to 999.

    4) Tell everyone in that net to do the same.




[12] FAQ & FGA

   Q:  I get a runtime error 17.  What gives?

   A:  You're running LordNet and your mailer across drives.  Sorry, but
       LordNet can't handle that.  Just copy LN*.Z* into a directory on
       your LordNet drive, and set that directory to the INCOMING FILES
       directory in LORDNET CONFIG, <E>dit Local CFG.  You can also copy
       the netmail files from a local directory to another drive without
       having to change anything in them.



   Q:  Not a Validated Coordinator pops up when I want to do one of the
       special NC menu options!

   A:  Here's what a validated coordinator means:

         * Your MAIN NODE (in Edit Local Configuration) must equal the
           node number of site #1 in the SITE.DAT.

         * Your BBS Name (in Edit Local Configuration) must equal the
           BBS Name of site #1 in the SITE.DAT (this is case sensitive).

         * You must be registered.


   Q:  How do I change my BBS name and/or node number without LordNet
       saying I'm not in the SITE.DAT?

   A:  Change it in the SITE EDITOR first, and then in EDIT LOCAL
       CONFIGURATION.


   Q:  OOPS!  I accidentally change my BBS name and/or node number in the
       Local Configuration, and now LordNet won't recognize me!

   A:  Text Edit your LORDNET.CFG back to the way the SITE.DAT thinks it is,
       and then change it in the SITE.DAT first.


   Q:  The whole net has adopted a new a completely reorganized SITE.DAT,
       where we've changed the site numbers of several nodes, and now
       LordNet won't process anything!

   A:  Tell all your sites to manually unzip the LN*.Z* file, copy the
       SITE.DAT into their main LordNet directory, and then process
       the packets.  Read the next tip for another solution!


   Q:  My site wants to shift the hubs down to the lower site #s, and
       thoroughly restructure the SITE.DAT.  How can I do this without
       making the other sysops in the league do anything?

   A:  First of all, make sure everyone is running 1.2L or later (use the
       UPDATE.ZIP!), and then use the <S>end a SITE.DAT in the SITE EDITOR.
       Choose the <R>estructuring option, and it will make one for each
       site.  (NOTE:  This is different from the <N>ew Site option for
       two reasons:  1), It packs the SITE.DAT out for everyone, and,
       2), it sends out a SITE.Dxx instead of SITE.DAT.  The "xx" is your
       League Tag!)


   Q:  My SITE.DAT, UPDATE.ZIPs, and TEAM.DATs don't get packed out!

   A:  Use <T>he Generator to create your ROUTE.CFG.


   Q:  Other Questions...

   A:  Read LordNet.doc 's section on Troubleshooting, and if your question
       isn't answered there, contact me!




  For even BETTER deals on Net registrations, call me voice!